Skip to content

build(deps): bump actions/setup-node from 4 to 5 #2381

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
wants to merge 1 commit into from
Closed

build(deps): bump actions/setup-node from 4 to 5 #2381

wants to merge 1 commit into from

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Sep 8, 2025 •
edited
Loading

Bumps actions/setup-node from 4 to 5.

Release notes

Sourced from actions/setup-node's releases.

v5.0.0

What's Changed

Breaking Changes

This update, introduces automatic caching when a valid packageManager field is present in your package.json. This aims to improve workflow performance and make dependency management more seamless. To disable this automatic caching, set package-manager-cache: false

steps:
- uses: actions/checkout@v5
- uses: actions/setup-node@v5
  with:
    package-manager-cache: false

Make sure your runner is on version v2.327.1 or later to ensure compatibility with this release. See Release Notes

Dependency Upgrades

New Contributors

Full Changelog: actions/setup-node@v4...v5.0.0

v4.4.0

What's Changed

Bug fixes:

Enhancement:

Dependency update:

New Contributors

Full Changelog: actions/setup-node@v4...v4.4.0

... (truncated)

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot dependabot bot added dependencies github_actions Pull requests that update GitHub Actions code labels Sep 8, 2025
@djc
Copy link
Member

djc commented Sep 8, 2025

@delta4chat want to have a look at what's going on with the netbsd build? @matheus23 same for WASM?

@matheus23
Copy link
Contributor

matheus23 commented Sep 10, 2025

Seems like the --locked option with cargo-binstall install wasm-bindgen-cli --locked --no-confirm doesn't seem to be working properly. Perhaps it's not finding the lockfile?

I find the underlying issue is described pretty clearly in the error message, but perhaps I can help with my own words: There are two versions of wasm-bindgen: The CLI and the library version. They need to match, otherwise they refuse to work together.
The library version is at 0.2.100, but the CLI version seems to be at 0.2.101, even though I specifically asked cargo binstall to use the Cargo.lock file to match the version (cargo-binstall install wasm-bindgen-cli --locked).

There's two easy ways to fix this: Upgrade the wasm-bindgen library version in the Cargo.lock and/or specify the CLI version exactly in rust.yml (cargo-binstall install wasm-bindgen-cli@0.2.101 --no-confirm).

@djc
Copy link
Member

djc commented Sep 10, 2025

There's two easy ways to fix this: Upgrade the wasm-bindgen library version in the Cargo.lock and/or specify the CLI version exactly in rust.yml (cargo-binstall install wasm-bindgen-cli@0.2.101 --no-confirm).

I think the former might have happened since then.

@djc
Copy link
Member

djc commented Sep 10, 2025

@dependabot rebase

@dependabot
build(deps): bump actions/setup-node from 4 to 5
e680bb6 
Bumps [actions/setup-node](https://github.com/actions/setup-node) from 4 to 5.
- [Release notes](https://github.com/actions/setup-node/releases)
- [Commits](actions/setup-node@v4...v5)

---
updated-dependencies:
- dependency-name: actions/setup-node
  dependency-version: '5'
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot force-pushed the dependabot/github_actions/actions/setup-node-5 branch from 91f9756 to e680bb6 Compare September 10, 2025 09:11
@djc djc enabled auto-merge September 10, 2025 09:16
@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Oct 20, 2025

Superseded by #2418.

@dependabot dependabot bot closed this Oct 20, 2025
auto-merge was automatically disabled October 20, 2025 13:46

Pull request was closed

@dependabot dependabot bot deleted the dependabot/github_actions/actions/setup-node-5 branch October 20, 2025 13:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@djc djc Awaiting requested review from djc djc is a code owner

@Ralith Ralith Awaiting requested review from Ralith Ralith is a code owner

@gretchenfrage gretchenfrage Awaiting requested review from gretchenfrage gretchenfrage is a code owner

Assignees

No one assigned

Labels

dependencies github_actions Pull requests that update GitHub Actions code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@djc @matheus23